Fibre Channel Forwarder load balancing system

ABSTRACT

A Fibre Channel Forwarder (FCF) load balancing system includes a Fibre Channel Forwarder (FCF) device that is coupled to a Fibre Channel (FC) networking device and the first server device. The FCF device groups a first link between the FC networking device and the FCF device with a second link between the FC networking device and the FCF device in response to receiving both a first fabric login accept on the first link that includes a first Worldwide Name (WWN) and a second fabric login accept on the second link that includes the first WWN. The FCF device provides at least a portion of traffic, received from the first server device that is logged in through the first link, through the second link.

BACKGROUND

The present disclosure relates generally to information handlingsystems, and more particularly to Fibre Channel Forwarder (FCF) loadbalancing for information handling systems.

As the value and use of information continues to increase, individualsand businesses seek additional ways to process and store information.One option available to users is information handling systems. Aninformation handling system generally processes, compiles, stores,and/or communicates information or data for business, personal, or otherpurposes thereby allowing users to take advantage of the value of theinformation. Because technology and information handling needs andrequirements vary between different users or applications, informationhandling systems may also vary regarding what information is handled,how the information is handled, how much information is processed,stored, or communicated, and how quickly and efficiently the informationmay be processed, stored, or communicated. The variations in informationhandling systems allow for information handling systems to be general orconfigured for a specific user or specific use such as financialtransaction processing, airline reservations, enterprise data storage,or global communications. In addition, information handling systems mayinclude a variety of hardware and software components that may beconfigured to process, store, and communicate information and mayinclude one or more computer systems, data storage systems, andnetworking systems.

Some information handling systems provide a Fibre Channel (FC) StorageArea Network (SAN) for the storage of data. In such systems, an FCswitch may be utilized to couple the FC SAN to servers via a FibreChannel Forwarder (FCF) that performs FC over Ethernet (FCoE)-to-FCprotocol conversions on Ethernet communications sent from the servers tothe FC SAN, as well as FC-to-FCoE protocol conversions on FCcommunications sent from the FC SAN to the servers. Such FCFs allow forservers that communicate via the Ethernet protocol to utilize FC SANsthat communicate via the FC protocol. However, the conventionalfunctionality of such FCFs raises a number of issues.

For example, servers in such systems may utilize a Converged NetworkAdapter (CNA) to communicate with an N_Port ID Virtualization (NPIV)Proxy Gateway (NPG) in the FCF in order to provide login communicationfor logging into the FC SAN, with the FCF converting those logincommunications and the NPG providing them to the FC switch in order tolog the server into the FC SAN. The NPG may establish links with the FCswitch via, for example, a plurality of virtual uplinks from servers oneach physical link provided between the NPG and the FC switch, and mayoperate to load balance logins received from servers via those links.However, in conventional FC SANs, traffic to and from servers isprovided only on the physical link used by the server to log in with theFC SAN. This results in uneven traffic balancing. or underutilization ofavailable bandwidth on other physical links between the NPG and the FCswitch.

Accordingly, it would be desirable to provide an improved FCF loadbalancing system.

SUMMARY

According to one embodiment, an Information Handling System (IHS)includes a plurality of ports; a processing system that is coupled tothe plurality of ports; and a memory system that is coupled to theprocessing system and that includes instructions that, when executed bythe processing system, cause the processing system to provide an N_PortID Virtualization (NPIV) Proxy Gateway (NPG) engine that is configuredto: group a first link between an FC networking device and a first portof the plurality of ports with a second link between the FC networkingdevice and a second port of the plurality of ports in response toreceiving both a first fabric login accept on the first link thatincludes a first Worldwide Name (WWN) and a second fabric login accepton the second link that includes the first WWN; and provide at least aportion of first traffic, received from a first server device that islogged in through the first link, through the second link.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic view illustrating an embodiment of an informationhandling system.

FIG. 2 is a schematic view illustrating an embodiment of a Fibre ChannelForwarder (FCF) load balancing system.

FIG. 3 is a schematic view illustrating an embodiment of a server devicein the FCF load balancing system of FIG. 2.

FIG. 4 is a schematic view illustrating an embodiment of an FCF devicein the FCF load balancing system of FIG. 2.

FIG. 5 is a schematic view illustrating an embodiment of an FCF deviceport grouping database in the FCF device of FIG. 2

FIG. 6 is a schematic view illustrating an embodiment of an FCnetworking device in the FCF port configuration system of FIG. 2.

FIG. 7 is a schematic view illustrating an embodiment of an FCnetworking device port grouping database in the FC networking device ofFIG. 2.

FIG. 8 is a flow chart illustrating an embodiment of a method for FCFload balancing.

FIG. 9 is a diagram illustrating an embodiment of the FCF load balancingduring the method of FIG. 8.

FIG. 10A is a schematic view illustrating an embodiment of informationbeing provided in the FC networking device port grouping database ofFIG. 7 during the method of FIG. 8.

FIG. 10B is a schematic view illustrating an embodiment of informationbeing provided in the FC networking device port grouping database ofFIG. 7 during the method of FIG. 8.

FIG. 11A is a schematic view illustrating an embodiment of informationbeing provided in the FCF device port grouping database of FIG. 5 duringthe method of FIG. 8.

FIG. 11B is a schematic view illustrating an embodiment of informationbeing provided in the FCF device port grouping database of FIG. 5 duringthe method of FIG. 8.

DETAILED DESCRIPTION

For purposes of this disclosure, an information handling system mayinclude any instrumentality or aggregate of instrumentalities operableto compute, calculate, determine, classify, process, transmit, receive,retrieve, originate, switch, store, display, communicate, manifest,detect, record, reproduce, handle, or utilize any form of information,intelligence, or data for business, scientific, control, or otherpurposes. For example, an information handling system may be a personalcomputer (e.g., desktop or laptop), tablet computer, mobile device(e.g., personal digital assistant (PDA) or smart phone), server (e.g.,blade server or rack server), a network storage device, or any othersuitable device and may vary in size, shape, performance, functionality,and price. The information handling system may include random accessmemory (RAM), one or more processing resources such as a centralprocessing unit (CPU) or hardware or software control logic, ROM, and/orother types of nonvolatile memory. Additional components of theinformation handling system may include one or more disk drives, one ormore network ports for communicating with external devices as well asvarious input and output (I/O) devices, such as a keyboard, a mouse,touchscreen and/or a video display. The information handling system mayalso include one or more buses operable to transmit communicationsbetween the various hardware components.

In one embodiment, IHS 100, FIG. 1, includes a processor 102, which isconnected to a bus 104. Bus 104 serves as a connection between processor102 and other components of IHS 100. An input device 106 is coupled toprocessor 102 to provide input to processor 102. Examples of inputdevices may include keyboards, touchscreens, pointing devices such asmouses, trackballs, and trackpads, and/or a variety of other inputdevices known in the art. Programs and data are stored on a mass storagedevice 108, which is coupled to processor 102. Examples of mass storagedevices may include hard discs, optical disks, magneto-optical discs,solid-state storage devices, and/or a variety other mass storage devicesknown in the art. IHS 100 further includes a display 110, which iscoupled to processor 102 by a video controller 112. A system memory 114is coupled to processor 102 to provide the processor with fast storageto facilitate execution of computer programs by processor 102. Examplesof system memory may include random access memory (RAM) devices such asdynamic RAM (DRAM), synchronous DRAM (SDRAM), solid state memorydevices, and/or a variety of other memory devices known in the art. Inan embodiment, a chassis 116 houses some or all of the components of IHS100. It should be understood that other buses and intermediate circuitscan be deployed between the components described above and processor 102to facilitate interconnection between the components and the processor102.

Referring now to FIG. 2, an embodiment of a Fibre Channel Forwarder(FCF) load balancing system 200 is illustrated. In the illustratedembodiment, the FCF load balancing system 200 includes a server device202 a that may be the IHS 100 discussed above with reference to FIG. 1and/or that may include some or all of the components of the IHS 100.For example, the server device 202 a may be one or more servers in aserver rack or server chassis, and one of skill in the art in possessionof the present disclosure will recognize that any number of servers maybe provided in the FCF load balancing system 200 and may operatesimilarly to the server devices discussed below. In the illustratedembodiment, the server device 202 a is coupled to a Fibre ChannelForwarder (FCF) device 204 that may be the IHS 100 discussed above withreference to FIG. 1 and/or that may include some or all of thecomponents of the IHS 100. For example, the FCF device 204 may beprovided by a switch or other networking device that is configured toreceive Ethernet communications from the server device 202 a, convertthose Ethernet communications to Fibre Channel (FC) communications forforwarding to an FC Storage Area Network (SAN), receive FCcommunications from the FC SAN, convert those FC communications toEthernet communications for forwarding to the server device 202 a,and/or perform other FCF device functionality know in the art.

In the illustrated embodiment, the FCF device 204 is coupled by aplurality of links (e.g., a link 205 a and a link 205 b) to an FCnetworking device 206 that may be the IHS 100 discussed above withreference to FIG. 1 and/or that may include some or all of thecomponents of the IHS 100. For example, the FC networking device 206 maybe provided by a FC switch that is configured to receive FCcommunications (e.g., initialed by the server device 202 a) from the FCFdevice 204, log the server device 202 a into an FC SAN, subsequentlyreceive FC communications (e.g., initialed by the server device 202 a)from the FCF device 204 to allow the server device 202 a to communicatewith the FC SAN, and perform a variety of other FC networking devicefunctionality that would be apparent to one of skill in the art inpossession of the present disclosure. In the illustrated embodiment, theFC networking device 206 is coupled to an FC storage system 208 that maybe the IHS 100 discussed above with reference to FIG. 1 and/or that mayinclude some or all of the components of the IHS 100. For example, theFC storage system 208 may be provided by a FC SAN that is configured toreceive FC communications from the server device 202 a through the FCnetworking device 206, send FC communications to the server device 202 athrough the FC networking device 206, and/or perform a variety of otherFC storage system functionality that would be apparent to one of skillin the art in possession of the present disclosure. While a specific FCFload balancing system 200 is illustrated and described below, one ofskill in the art in possession of the present disclosure will recognizethat the teachings of the present disclosure will be beneficial for avariety of FC systems that would be apparent to one of skill in the artin possession of the present disclosure and, as such, a wide variety ofmodifications to the number, types, and orientation of devices in theFCF load balancing system 200 will fall within the scope of the presentdisclosure as well. For example, as illustrated in FIG. 2, the FCFdevice 204 may be coupled to an additional server device 202 b.

Referring now to FIG. 3, an embodiment of a server device 300 isillustrated that may be the server devices 202 a and 202 b discussedabove with reference to FIG. 2. As such, the server device 300 may bethe IHS 100 discussed above with reference to FIG. 1 and/or may includesome or all of the components of the IHS 100, and in specific examplesmay be one or more servers in a server rack or server chassis. In theillustrated embodiment, the server device 300 includes a chassis 302that houses the components of the server device 300, only some of whichare illustrated in FIG. 3. For example, the chassis 302 may house aprocessing system (not illustrated, but which may include the processor102 discussed above with reference to FIG. 1) and a memory system (notillustrated, but which may include the system memory 114 discussed abovewith reference to FIG. 1) that includes instructions that, when executedby the processing system, cause the processing system to provide anadapter engine 304 that is configured to perform the functions of theadapter engines and server devices discussed below.

The chassis 302 may also house a storage system (not illustrated, butwhich may include the storage device 108 discussed above with referenceto FIG. 1) that is coupled to the adapter engine 304 (e.g., via acoupling between the storage system and the processing system) and thatmay include a storage subsystem 306 that is configured to store the datautilized as discussed below. However, in some embodiments the storagesubsystem 306 may be omitted. The chassis 302 may also house acommunication subsystem 308 that is coupled to the adapter engine 304(e.g., via a coupling between the communication subsystem 308 and theprocessing system) and that may include a Network Interface Controller(NIC), a wireless communication devices, one or more ports (e.g., a port308 a), and/or other communication components that would be apparent toone of skill in the art in possession of the present disclosure.Furthermore, in some embodiments, components of the adapter engine 304and/or the communication subsystem 308 may be provided by a ConvergedNetwork Adapter (CNA) that performs the functionality of the adapterengines and/or server devices discussed below. However, in otherembodiments, the adapter engine 304 and/or communication subsystem 308may be utilized to provide other types of adapters (e.g., Host BusAdapters (HBAs)) while remaining within the scope of the presentdisclosure. While a specific server device 300 has been described, oneof skill in the art in possession of the present disclosure willrecognize that the server device 300 may include a variety of othercomponents that perform conventional server device functionality, aswell as the functionality described below, while remaining within thescope of the present disclosure.

Referring now to FIG. 4, an embodiment of a Fibre Channel Forwarder(FCF) device 400 is illustrated that may be the FCF device 204 discussedabove with reference to FIG. 2. As such, the FCF device 400 may be theIHS 100 discussed above with reference to FIG. 1 and/or may include someor all of the components of the IHS 100, and in specific examples may bea switch, a gateway, or other networking device. In the illustratedembodiment, the FCF device 400 includes a chassis 402 that houses thecomponents of the FCF device 400, only some of which are illustrated inFIG. 4. For example, the chassis 402 may house a processing system (notillustrated, but which may include the processor 102 discussed abovewith reference to FIG. 1) and a memory system (not illustrated, butwhich may include the system memory 114 discussed above with referenceto FIG. 1) that includes instructions that, when executed by theprocessing system, cause the processing system to provide an conversionengine 404 that is configured to perform the functions of the conversionengines and FCF devices discussed below. In a specific example, theconversion engine 404 may include an N_Port ID Virtualization (NPIV)Proxy Gateway (NPG) engine that operates as discussed below, althoughother conversion engines may fall within the scope of the presentdisclosure as well. In another example, the conversion engine 404 mayinclude an FCF load balancing engine 405 that is configured to performthe functions of the load balancing engines and FCF devices discussedbelow such as, e.g., grouping ports on the FCF device 400 and balancingtraffic through those grouped ports.

The chassis 402 may also house a storage system (not illustrated, butwhich may include the storage device 108 discussed above with referenceto FIG. 1) that is coupled to the conversion engine 404 (e.g., via acoupling between the storage system and the processing system) and thatmay include an FCF device port grouping database 406 that is configuredto store the data utilized as discussed below. The chassis 402 may alsohouse a communication subsystem 408 that is coupled to the conversionengine 404 (e.g., via a coupling between the communication subsystem 408and the processing system) and that may include a Network InterfaceController (NIC), a wireless communication devices, ports, and/or othercommunication components that would be apparent to one of skill in theart in possession of the present disclosure. For example, in theillustrated embodiment, the communication subsystem 408 includes aplurality of ports (e.g., the ports 408 a, 408 b, 408 c, 408 d, and upto 408 e) that may be coupled to an FC networking device, another FCFforwarder, and/or a server device as discussed below. Furthermore, insome embodiments, components of the conversion engine 404 and/or thecommunication subsystem 408 may provide an NPG that performs thefunctionality of the conversion engines and/or server devices discussedbelow. However, as discussed above, the conversion engine 404 may beutilized to provide for other types of conversions while remainingwithin the scope of the present disclosure. While a specific FCF device400 has been described, one of skill in the art in possession of thepresent disclosure will recognize that the FCF device 400 may include avariety of other components that perform conventional FCF devicefunctionality, as well as the functionality described below, whileremaining within the scope of the present disclosure.

Referring now to FIG. 5, an embodiment of an FCF device port groupingdatabase 500 is illustrated. In an embodiment, the FCF device portgrouping database 500 may be the FCF device port grouping database 406discussed above with reference to FIG. 4. In a specific example, the FCFdevice 204 and the FC networking device 206 may utilize a linkaggregation protocol and the FCF device port grouping database 500 mayinclude an FCF virtual trunk instance map that includes informationabout ports in a trunk group that may be defined by FC virtual trunking,as discussed below. However, one of skill in the art in possession ofthe present disclosure will recognize that other link aggregationprotocols will fall within the scope of the present disclosure as well.In the illustrated example, the FCF device port grouping database 500includes an FCF device virtual trunk instance mapping table 502 havingmapping table entries 502 a, 502 b, 502 c, and up to 502 d. For example,for each FCF virtual trunk instance mapping table entry 502 a-d, themapping table 502 may include a Fibre Channel (FC) identifier (FCID)column 504, a login type column 506, a port identifier column 508, and aFC networking device identifier column 510. However, one of skill in theart in possession of the present disclosure will recognize that the FCFdevice port grouping database 500 and/or the FCF device virtual trunkinstance mapping table 502 may include and/or store other information toenable the functionality discussed below while remaining within thescope of the present disclosure.

Referring now to FIG. 6, an embodiment of a Fibre Channel (FC)networking device 600 is illustrated that may be the FC networkingdevice 206 discussed above with reference to FIG. 2. As such, the FCnetworking device 600 may be the IHS 100 discussed above with referenceto FIG. 1 and/or may include some or all of the components of the IHS100, and in specific examples may be an FC switch. In the illustratedembodiment, the FC networking device 600 includes a chassis 602 thathouses the components of the FC networking device 600, only some ofwhich are illustrated in FIG. 6. For example, the chassis 602 may housea processing system (not illustrated, but which may include theprocessor 102 discussed above with reference to FIG. 1) and a memorysystem (not illustrated, but which may include the system memory 114discussed above with reference to FIG. 1) that includes instructionsthat, when executed by the processing system, cause the processingsystem to provide an FC engine 604 that is configured to perform thefunctions of the FC engines and FC networking devices discussed below.In another example, the FC engine 604 may include an FC load balancingengine 605 that is configured to perform the functions of the loadbalancing engines and FC networking devices discussed below such asgrouping ports on the FC networking device 600 and balancing trafficthrough those grouped ports.

The chassis 602 may also house a storage system (not illustrated, butwhich may include the storage device 108 discussed above with referenceto FIG. 1) that is coupled to the FC engine 604 (e.g., via a couplingbetween the storage system and the processing system) and that mayinclude an FC networking device port grouping database 606 that isconfigured to store the data utilized as discussed below. The chassis602 may also house a communication subsystem 608 that is coupled to theFC engine 604 (e.g., via a coupling between the communication subsystem608 and the processing system) and that may include a Network InterfaceController (NIC), a wireless communication devices, ports, and/or othercommunication components that would be apparent to one of skill in theart in possession of the present disclosure. For example, in theillustrated embodiment, the communication subsystem 608 includes aplurality of ports 608 a, 608 b, and up to 608 c, that may be coupled toan FCF device as well as an FC SAN (e.g., the FC storage system 208), asdiscussed herein. While a specific FC networking device 600 has beendescribed, one of skill in the art in possession of the presentdisclosure will recognize that the FC networking device 600 may includea variety of other components that perform conventional FC networkingdevice functionality, as well as the functionality described below,while remaining within the scope of the present disclosure.

Referring now to FIG. 7, an embodiment of an FC networking device portgrouping database 700 is illustrated. In an embodiment, the FCnetworking device port grouping database 700 may be the FC networkingdevice port grouping database 606 discussed above with reference to FIG.6. In a specific example, and as discussed above, the FCF device 204 andthe FC networking device 206 may utilize a link aggregation protocol,and the FC networking device port grouping database 700 may include anFC networking device virtual trunk instance map that includesinformation about ports in a trunk group that may be defined by FCvirtual trunking, as discussed below. However, one of skill in the artin possession of the present disclosure will recognize that other linkaggregation protocols will fall within the scope of the presentdisclosure as well. In the illustrated example, the FC networking deviceport grouping database 700 includes an FC networking device virtualtrunk instance mapping table 702 having mapping table entries 702 a, 702b, 702 c, and up to 702 d. For example, for each FC networking devicevirtual trunk instance mapping table entry 702 a-d, the mapping tablemay include a Fibre Channel (FC) identifier (FCID) column 704, a logintype column 706, a port identifier column 708, and a FCF identifiercolumn 710. However, one of skill in the art in possession of thepresent disclosure will recognize that the FC networking device portgrouping database 700 and/or the FC networking device virtual trunkinstance mapping table 702 may include and/or store other information toenable the functionality discussed below while remaining within thescope of the present disclosure.

Referring now to FIG. 8, an embodiment of a method 800 for FCF loadbalancing is illustrated. As discussed above, when a server establishesa virtual link through a physical link between a FCF device and a FCnetworking device, traffic to and from that server is provided over thephysical link through which that server is logged in, even though theremay be other physical links between the FCF device and the FC networkingdevice through which that traffic may be provided. This results inuneven traffic balancing between the FCF device and the FC networkingdevice, and/or underutilization of available bandwidth. The systems andmethod of the present disclosure remedy these deficiencies by groupingthe physical links as a single link such that the traffic may be loadbalanced among the physical links of that group. For example, the FCnetworking device may group the FC networking device ports togetherbased on the node FCF identifier present in a fabric login (FLOGI)received at each port, while the FCF device may group the FCF deviceports together based on the FC networking device identifier provided ina FLOGI accept (FLOGI ACC). The FCF device and the FC networking devicemay then use the grouped ports to load balance traffic among the memberof the group.

The method 800 begins at block 802 where an FCF device provides a firstfabric login to an FC networking device through a first FCF port. In anembodiment of block 802 and with reference to a FCF load balancingdiagram 900 in FIG. 9, the conversion engine 404 of the FCF device 204may transmit a FLOGI 902 a through its port 408 a to the port 608 a ofthe FC networking device 206 via a link initialized between the ports408 a and 608 a. The FLOGI 902 a may include FCF device informationabout the FCF device 204, and FCF device port information about the port408 a. For example, the FLOGI 902 a may include an FCF device identifiersuch as, for example, a node worldwide name (NWWN). The FLOGI 902 a mayalso include an FCF port identifier for the port 408 a such as, forexample, a port worldwide name (PWWN), and/or any other FCF deviceinformation and/or FCF port information that would be apparent to one ofskill in the art in possession of the present disclosure.

The method 800 then proceeds to block 804 where the FCF device providesa second fabric login to the FC networking device through a second FCFport. In an embodiment of block 804 and with reference to the FCF loadbalancing diagram 900 in FIG. 9, the FCF device 204 may transmit a FLOGI902 b through its port 408 b to the port 608 b of the FC networkingdevice 206. The FLOGI 902 b may include FCF device information about theFCF device 204, and FCF device port information about the port 408 b.For example, the FLOGI 902 b may include an FCF device identifier suchas, for example, an NWWN. In an embodiment, the NWWN provided in theFLOGI 902 b may be the same as the NWWN provided in the FLOGI 902 a. TheFLOGI 902 b may also include an FCF port identifier of the port 608 bsuch as, for example, a PWWN, and/or any other FCF device informationand/or FCF port information that would be apparent to one of skill inthe art in possession of the present disclosure.

The method 800 then proceeds to block 806 where the FC networking deviceprovides a first fabric login accept through a first FC networkingdevice port, and the FCF device 204 receives that first fabric loginaccept via its first FCF port (i.e., in response to sending the firstfabric login at block 802.) In an embodiment of block 806 and withreference to the FCF load balancing diagram 900 in FIG. 9, the FCnetworking device 206 provides a first FLOGI link service accept (FLOGILS_ACC) 904 a through its port 608 a to the port 408 a of the FCF device204 in response to the received FLOGI 902 a. One of skill in the art inpossession of the present disclosure will recognize that block 806 ofmethod 800 may be performed before block 804 (i.e., the first fabriclogin accept may be received before the second fabric login is sent.)The FLOGI LS_ACC 904 a may include FC networking device informationabout the FC networking device 206. For example, the FLOGI LS_ACC 904 amay include an FC networking device identifier such as, for example, afabric worldwide name (FWWN). The FLOGI LS_ACC 904 a may also include aFibre Channel (FC) identifier (FCID) that the FC networking device 206assigns to the node port (N_Port) port 408 a. As would be understood byone of skill in the art in possession of the present disclosure, theFCID for the port 408 a may be a unique identifier within the FC SAN forthat port 408 a. While specific FC networking device information isdiscussed above, one of skill in the art in possession of the presentdisclosure would recognize that other FC networking device informationmay be provided with the FLOGI LS_ACC 904 a without departing from thescope of the present disclosure.

The method 800 then proceeds to block 808 where the FC networking deviceprovides a second fabric login accept through a second FC networkingdevice port, and the FCF device 204 receives that second fabric loginaccept via its second FCF port (i.e., in response sending to the secondfabric login at block 804.) In an embodiment of block 808 and withreference to the FCF load balancing diagram 900 in FIG. 9, the FCnetworking device 206 provides a second FLOGI LS_ACC 904 b through itsport 608 b to the port 408 b of the FCF device 204 in response to thereceived FLOGI 902 b. The FLOGI LS_ACC 904 b may include FC networkingdevice information about the FC networking device 206. For example, theFLOGI LS_ACC 904 b may include an FC networking device identifier suchas, for example, a FWWN. In an embodiment, the FWWN provided with theFLOGI LS_ACC 904 b may be the same FWWN provided with the FLOGI LS_ACC904 a. The FLOGI LS_ACC 904 b may also include an FCID that the FCnetworking device 206 assigns to the N_Port (e.g., port 408 b). Whilespecific FC networking device information is discussed above, one ofskill in the art in possession of the present disclosure would recognizethat other FC networking device information may be provided with theFLOGI LS_ACC 904 b without departing from the scope of the presentdisclosure.

The method 800 then proceeds to block 810 where the FC networking devicegroups the first FC networking device port and the second FC networkingdevice port. In an embodiment of block 810 and with reference to the FCFload balancing diagram 900 of FIG. 9, the FC networking device 206 maygroup its ports 608 a and 608 b as a trunk group 914 a (e.g., as definedby FC virtual trunking, discussed above) based on, for example, the NWWNreceived with the FLOGI 902 a and the NWWN received with the FLOGI 902 bbeing the same. The trunk group 914 a may be stored in the FC networkingdevice port grouping database 606. In an embodiment, and with referenceto the FC networking device port grouping database 700 of FIG. 10A, theFC networking device 206 may create a virtual trunk instance that mapsthe FCIDs assigned to the N_Port via the trunk group 914 a, login types(e.g., FLOGI or fabric discovery (FDISC)), and the NWWN to the ports ofthe trunk group 914 a. The FC networking device virtual trunk instancemapping table 702 illustrates an example of the FC networking devicevirtual trunk instance map. For example, row 702 a of the FC networkingdevice virtual trunk instance mapping table 702 illustrates how the FCload balancing engine 605 may operate to associate the trunk group 914 awith a virtual trunk instance by associating the port 608 a to the firstFCID (“FCID1”) assigned to port 408 a, which is a “FLOGI” login type andhas an NWWN of the FCF device 204. Furthermore, row 702 b of the FCnetworking device virtual trunk instance mapping table 702 illustrateshow the FC load balancing engine 605 may also associate the port 608 bwith the second FCID (“FCID2”) assigned to port 408 b, which is a“FLOGI” login type and has an NWWN of the FCF device 204.

The method 800 then proceeds to block to block 812 where the FCF devicegroups the first FCF device port and the second FCF device port. In anembodiment of block 812 and with reference to the FCF load balancingdiagram 900 of FIG. 9, the FCF device 204 may group the ports 408 a and408 b as a trunk group 914 b (e.g., as defined by FC virtual trunking,discussed above) based on, for example, the FWWN received with the FLOGILS_ACC 904 a and the FWWN received with the FLOGI LS_ACC 904 b being thesame. The trunk group 914 b may be stored in the FCF device portgrouping database 406. In an embodiment, and with reference to the FCFdevice port grouping database 500 of FIG. 11A, the FCF device 204 maymap the FCIDs assigned to the N_Ports in the trunk group 914 b,associated login types (e.g., FLOGI or FDISC), and the FWWN to the portsof the trunk group 914 b. The FCF device virtual trunk instance mappingtable 502 illustrates an example of the FCF device virtual trunkinstance map. For example, row 502 a of the FCF device virtual trunkinstance mapping table 502 illustrates how the FCF load balancing engine405 may operate to associate the trunk group 914 b with the virtualtrunk instance described above, by associating the port 408 a to thefirst FCID (“FCID1”) assigned to port 408 a, which is a “FLOGI” logintype and has an FWWN of the FC networking device 206, and associatingthe port 408 b to the second FCID (“FCID2”) assigned to port 408 b,which is a “FLOGI” login type and corresponds to an FWWN of the FCnetworking device 206.

The method 800 then proceeds to block 814 where a server device logsinto the FC networking device via the FCF device. In an embodiment ofblock 814 and with reference to the FCF load balancing diagram 900 ofFIG. 9, one or more server device (e.g., server device 202 a and/or 202b) may login to the FC SAN via the FCF device 204. For example, theadapter engine 304 of the server device 202 a may provide, through theport 308 a (which may be an N_Port), a FLOGI 906 a to the port 408 c(which may be an F_Port) of the FCF device 204. The FLOGI 906 a mayinclude server device information about the server device 202 a, andserver device port information about the port 308 a. For example, theFLOGI 906 a may include a server device identifier such as, for example,a NWWN. The FLOGI 906 a may also include a server port identifier forthe port 308 a such as, for example, a PWWN and/or any other serverdevice information and/or server device port information that would beapparent to one of skill in the art in possession of the presentdisclosure.

The FCF load balancing engine 405 may then determine through which ofthe N_Ports (e.g., ports 408 a and 408 b) the server device 202 a shouldlog into the FC networking device. For example, the FCF load balancingengine 405 may use login based load balancing to determine which ofports 408 a and 408 b has the fewest number of login sessions, or mayuse any other login based load balancing technique that would beapparent to one of skill in the art in possession of the presentdisclosure. In the illustrated example of FIG. 9, the FCF load balancingengine 405 may determine that the FLOGI 906 a should be serviced by thelink between port 408 a and port 608 a. The conversion engine 404 maythen generate an FDISC 908 a that includes FCF device information aboutthe FCF device 204 and server device port information about the port 308a. For example, the FDISC 908 a may include an FCF device identifiersuch as, for example, a NWWN. The FDISC 908 a may also include a serverport identifier for the port 308 a such as, for example, a PWWN and/orany other FCF device information and/or server device information thatwould be apparent to one of skill in the art in possession of thepresent disclosure.

The FC networking device 206 then provides a first FDISC link serviceaccept (FDISC LS_ACC) 910 a through the port 608 a to the port 408 a inresponse to the received FDISC 908 a. The FDISC LS_ACC 908 a may includeFC networking device information about the FC networking device 206. Forexample, the FDISC LS_ACC 908 a may include an FC networking deviceidentifier such as, for example, an FWWN. The FDISC LS_ACC 908 a mayalso include an FCID that the FC networking device 206 assigns to theN_Port (e.g., port 308 a). The conversion engine 404 may generate aFLOGI LS_ACC 912 a that is provided through the port 408 c to the port308 a. The FLOCI LS_ACC 912 a may include the FCID, the FWWN, and/or anyother FCF device information or FC networking device information thatwould be apparent to one of skill in the art in possession of thepresent disclosure.

Similarly, the adapter engine 304 of the server device 202 b mayprovide, through the port 308 a (which may be an N_Port), a FLOGI 906 bto the port 408 d (which may be an F_Port) of the FCF device 204. TheFLOGI 906 b may include server device information about the serverdevice 202 b and server device port information about the port 308 a.For example, the FLOGI 906 b may include a server device identifier suchas, for example, a NWWN. The FLOGI 906 b may also include a server portidentifier for the port 308 a such as, for example, a PWWN and/or anyother server device information and/or server device port informationthat would be apparent to one of skill in the art in possession of thepresent disclosure.

The FCF load balancing engine 405 may then determine which of N_Ports(e.g., ports 408 a and 408 b) the server device 202 a should utilize tologin. For example, the FCF load balancing engine 405 may use loginbased load balancing to determine which port of ports 408 a and 408 bhas the fewest number of login sessions, or may use any other loginbased load balancing technique that would be apparent to one of skill inthe art in possession of the present disclosure. In the illustratedexample of FIG. 9, the FCF load balancing engine 405 may determine thatthe FLOGI 906 b should be serviced by the link between the port 408 band the port 608 b. The conversion engine 404 may then generate an FDISC908 b that includes FCF device information about the FCF device 204 andserver device port information about the port 308 a of the server device202 b. For example, the FDISC 908 b may include an FCF device identifiersuch as, for example, the NWWN. The FDISC 908 b may also include aserver port identifier for the port 308 a of the server device 202 bsuch as, for example, a PWWN and/or any other FCF device informationand/or server device information that would be apparent to one of skillin the art in possession of the present disclosure.

The FC networking device 206 then provides a second FDISC LS_ACC 910 bthrough the port 608 b to the port 408 b in response to the receivedFDISC 908 b. The FDISC LS_ACC 908 b may include FC networking deviceinformation about the FC networking device 206. For example, the FDISCLS_ACC 908 b may include an FC networking device identifier (e.g., theFWWN). The FDISC LS_ACC 908 b may also include an FCID that the FCnetworking device 206 assigns to the port 308 a of the server device 202b. The conversion engine 404 may generate a FLOGI LS_ACC 912 b that isprovided through the port 408 d to the port 308 a of the server device202 b. The FLOCI LS_ACC 912 b may include the FCID, the FWWN, and/or anyother FCF device information and/or FC networking device informationthat would be apparent to one of skill in the art in possession of thepresent disclosure.

In an embodiment, and with reference to the FC networking device portgrouping database 700 of FIG. 10B, the FC networking device 206 may map,to the virtual trunk instance, the FCIDs assigned to the N_Ports of theserver devices 202 a and 202 b, login types (e.g., FLOGI or FDISC)), andthe NWWN to the ports of the trunk group 914 a. The FC networking devicevirtual trunk instance mapping table 702 illustrates an example of theFC networking device virtual trunk instance map. For example, row 702 cof the FC networking device virtual trunk instance map illustrates howthe FC load balancing engine 605 may operate to associate the trunkgroup 914 a with a virtual trunk instance by associating the virtualtrunk instance with the third FCID (“FCID3”) assigned to port 308 a ofserver device 202 a, which is a “FDISC” login type and has an NWWN ofthe FCF device 204. The FC networking device virtual trunk instance mapin FIG. 10B also illustrates how the FC load balancing engine 605 mayassociate the virtual trunk instance to the fourth FCID (“FCID4”)assigned to port 308 a of the server device 202 b, which is an “FDISC”login type and has an NWWN of the FCF device 204.

In an embodiment and referring to the FCF device port grouping database500 of FIG. 11A, the FCF device 204 may map in the FCF device virtualtrunk instance the FCIDs assigned to the N_Ports of the server devices202 a and 202 b in the trunk group 914 b, associated login types (e.g.,FLOGI or FDISC), and the FWWN to the ports of the trunk group 914 b. TheFCF device virtual trunk instance mapping table 502 illustrates the FCFdevice virtual trunk instance map. For example, row 502 c of the FCnetworking device virtual trunk instance map illustrates how the FCFload balancing engine 405 may associate the port 408 c with a third FCID(“FCID3”) assigned to port 308 a of server device 202 a, which is a“FLOGI” login type and has the FWWN of the FC networking device 206. TheFCF device virtual trunk instance map in FIG. 11B also illustrates howthe FCF load balancing engine 405 may associate the port 408 d to thefourth FCID (“FCID4”) assigned to port 308 a of server device 202 b,which is a “FLOGI” login type and corresponds with the FWWN of the FCnetworking device 206.

The method 800 then proceeds to block 816 where at least a portion offirst traffic, which is received from the first server device that islogged in through the first link to the FC networking device, isprovided through the second link to the FC networking device. Inembodiment of block 816, the FCF device 204 may receive first trafficfrom the server device 202 a and/or second traffic from server device202 b. The conversion engine 404 may then convert the first trafficand/or the second traffic from a first protocol to a second protocol.For example, the conversion engine 404 may receive Ethernetcommunications from the server device 202 a and/or 202 b, and convertthose Ethernet communications to Fibre Channel (FC) communications forforwarding to the FC SAN. The FCF load balancing engine 405 may alsoload balance the first traffic over any of the ports 408 a and 408 b inthe trunk group 914 b. For example, the FCF load balancing engine 405may hash the first traffic among the ports 408 a and 408 b of the trunkgroup 914 b, and/or perform any other load balancing algorithm thatwould be apparent to one of skill in the art in possession of thepresent disclosure. The FC networking device 206 may then forward thefirst traffic received at the ports 608 a and 608 b to the destinationin the FC storage system 208.

Similarly, any traffic that is being provided by the FC networkingdevice 206 to the server device 202 a that is logged in to the FCnetworking device 206 though the link on the ports 408 a and 608 a maybe load balanced by the FC load balancing engine 605 such that thetraffic is provided over the link on ports 408 a and 608 a. and providedover the link on ports 408 b and 608 b, according to the trunk group 914a. The FCF device 204 receives the traffic, converts the traffic to aprotocol the FCF device 204 can use to communicate with the serverdevice 202 a, and provides the traffic to the server device 202 a overthe link between port 408 c and port 308 a of server device 202 a.

The method 800 may then proceed to decision block 818 where it isdetermined whether a link failure has occurred on the trunk group. In anembodiment of decision block 818, if a link failure has not occurred themethod 800 may return to block 816 where traffic is provided between theserver device(s) 202 a and/or 202 b and the FC networking device 206.If, at decision block 8181, it is determined that a link failure hasoccurred to a link of the trunk group, the method 800 may proceed toblock 820 where a link failure action is performed to the trunk group.In an embodiment of block 820, when only a trunk group has beenestablished that groups the ports 408 a and 408 b at the FCF device 204and groups the ports 608 a and 608 b at the FC networking device 206,and a link failure occurs, then sessions/logins that are provided viathat link will end. For example, if the link between ports 408 a and 608a fails, then the ability of the server device 202 a to login throughthe link between ports 408 a and 608 b will be removed, and a re-loginmay occur at the link between ports 408 b and 608 b (which is stillactive.)

In an embodiment of block 820, when a virtual trunk instance isestablished and a link failure is detected, only the FLOGI of thecorresponding port will be removed from the virtual trunk instance. Assuch, all other FCIDs may remain intact because the virtual trunkinstance is still active. Thus, the virtual trunk instance may only bedown if all of the ports of the trunk group are down (e.g., the links onports 408 a and 408 b of trunk group 914 b have failed.) For example, ifthe link between ports 408 a and 608 a goes down, the FC load balancingengine 605 may remove the FC networking device virtual trunk instancemapping table entry 702 a for the first FCID (FCID1), which correspondswith the FLOGI 902 a provided by port 408 a, from the FC networkingdevice virtual trunk instance mapping table 702, and all other entriesmay remain in the FC networking device virtual trunk instance mappingtable 702. Similarly, the FCF load balancing engine 405 may remove theFCF device virtual trunk instance mapping table entry 502 a for thefirst FCID (FCID1), which corresponds with the FLOGI 902 a provided byport 408 a, from the FCF device virtual trunk instance mapping table502, and all other entries may remain in the FCF device virtual trunkinstance mapping table 502. In such a scenario, the server device 202 athat logged in through the link between ports 408 a and 608 a does nothave to re-login through another link because it is mapped to thevirtual trunk instance. Therefore, the FCF load balancing engine 405 maycontinue to provide traffic between the server device 202 a and the FCnetworking device 206 through the link between ports 408 b and 608 b.

Thus, systems and methods have been described that provide for FCF loadbalancing by grouping physical links between and FC networking deviceand an FCF device as a single link such that traffic may be loadbalanced among the links of that group. The FC networking device maygroup the FC networking device ports together based on the node FCFidentifier present in a FLOGI received at each FC networking deviceport. Similarly, the FCF device may group the FCF device ports togetherbased on the FC networking device identifier provided in a FLOGI ACC.The FCF device and the FC networking device may use the grouped ports toload balance traffic among the links of the group, which provides moreeven traffic balancing and utilization of available bandwidth on otherphysical links between the FCF device and the FC networking device.

Although illustrative embodiments have been shown and described, a widerange of modification, change and substitution is contemplated in theforegoing disclosure and in some instances, some features of theembodiments may be employed without a corresponding use of otherfeatures. Accordingly, it is appropriate that the appended claims beconstrued broadly and in a manner consistent with the scope of theembodiments disclosed herein.

What is claimed is:
 1. A Fibre Channel Forwarder (FCF) load balancingsystem, comprising: a Fibre Channel (FC) networking device; a firstserver device; and an FC Forwarder (FCF) device that is coupled to theFC networking device and the first server device, wherein the FCF deviceis configured to: group a first link between the FC networking deviceand the FCF device with a second link between the FC networking deviceand the FCF device in response to receiving both a first fabric loginaccept on the first link that includes a first Worldwide Name (WWN)associated with the FC networking device and a second fabric loginaccept on the second link that includes the first WWN associated withthe FC networking device as a first trunk group, wherein the receivingthe first fabric login accept completes a first fabric login between theFCF device and the FC networking device via the first link, and whereinthe receiving the second fabric login accept completes a second fabriclogin between the FCF device and the FC networking device via the secondlink; receive a third fabric login request from the first server device;select the first link over the second link through which to log thefirst server device into the FC networking device based on the thirdfabric login request; establish a third fabric login between the firstserver device and the FC networking device via the FCF device and thefirst link between the FC networking device and the FCF device; andprovide at least a portion of first traffic, received from the firstserver device that is only logged in to the FC networking device throughthe first link between the FC networking device and the FCF device,through the second link between the FC networking device and the FCFdevice when the first link and the second link are in the first trunkgroup.
 2. The FCF load balancing system of claim 1, wherein the FCFdevice is further configured to: establish a fourth fabric login betweenthe first server device and the FC networking device via the FCF deviceand the second link between the FC networking device and the FCF devicewhen the first link is not available.
 3. The FCF load balancing systemof claim 1, wherein the FCF device is further configured to: group,subsequent to the grouping of the first link and the second link, athird link between the FC networking device and the FCF device with thefirst link and the second link in response to receiving a third fabriclogin accept on the third link that includes the first WWN associatedwith the FC networking device such that the third link is added to thefirst trunk group, wherein the receiving the third fabric login acceptcompletes a fourth fabric login that is between the FCF device and theFC networking device via the third link.
 4. The FCF load balancingsystem of claim 1, wherein the FC networking device is configured to:group the first link between the FC networking device and the FCF devicewith the second link between the FC networking device and FCF device asa second trunk group in response to receiving both a first fabric loginrequest on the first link that includes a second WWN associated with theFCF device and a second fabric login request on the second link thatincludes the second WWN associated with the FCF device, wherein thesecond trunk group causes the FC networking device to accept at leastthe portion of the first traffic from the first server device on thesecond link through which the first server device is not logged in tothe FC networking device.
 5. The FCF load balancing system of claim 4,wherein the FCF device is further configured to: generate a first map ofa virtual trunk instance that includes a virtual trunk identifier mappedto the first link and the second link, wherein the first map includesthe virtual trunk identifier that is associated with a first FCidentifier assigned to a first node port of the FCF device providing thefirst link, the first WWN included with the first link, and a login typeof the first link, and wherein the virtual trunk identifier isassociated with a second FC identifier that is assigned to a second nodeport of the second link, the first WWN of the second link, and a logintype of the second link, and wherein the FC networking device isconfigured to: generate a second map of the virtual trunk instance thatincludes the virtual trunk identifier mapped to the first link and thesecond link, wherein the second map includes the virtual trunkidentifier that is associated with the first FC identifier that isassigned to the first node port of the FCF device providing the firstlink, the second WWN included with the first link, and the login type ofthe first link, and wherein the virtual trunk identifier is associatedwith the second FC identifier that is assigned to the second node portof the second link, the second WWN of the second link, and the logintype of the second link.
 6. The FCF load balancing system of claim 5,wherein the virtual trunk instance is removed in response to identifyingthat all links in the virtual trunk instance are no longer available. 7.The FCF load balancing system of claim 5, wherein the FCF device isfurther configured to: remove the first link from the first map of thevirtual trunk instance in response to identifying that the first link isno longer available, and wherein the FC networking device is configuredto: remove the first link from the second map of the virtual trunkinstance in response to identifying that the first link is no longeravailable.
 8. The FCF load balancing system of claim 7, wherein the FCFdevice is further configured to: provide, in response to identifyingthat the first link is no longer available, traffic from the firstserver device through the second link without logging out the firstserver device.
 9. An Information Handling System (IHS), comprising: aplurality of ports; a processing system that is coupled to the pluralityof ports; and a memory system that is coupled to the processing systemand that includes instructions that, when executed by the processingsystem, cause the processing system to provide an N_Port IDVirtualization (NPIV) Proxy Gateway (NPG) engine that is configured to:group a first link between a Fibre Channel (FC) networking device and afirst port of the plurality of ports with a second link between the FCnetworking device and a second port of the plurality of ports inresponse to receiving both a first fabric login accept on the first linkthat includes a first Worldwide Name (WWN) associated with the FCnetworking device and a second fabric login accept on the second linkthat includes the first WWN associated with the FC networking device asa first trunk group, wherein the receiving the first fabric login acceptcompletes a first fabric login between the first port and the FCnetworking device via the first link, and wherein the receiving thesecond fabric login accept completes a second fabric login between thesecond port and the FC networking device via the second link; receive athird fabric login request from a first server device on a third port ofthe plurality of ports; select the first link on the first port over thesecond link on the second port through which to log the first serverdevice into the FC networking device based on the third fabric loginrequest; establish a third fabric login between the first server deviceand the FC networking device via the third port and the first linkbetween the FC networking device and the first port; and provide atleast a portion of first traffic, received from the first server devicevia the third port and that is only logged in to the FC networkingdevice through the first link between the FC networking device and thefirst port, through the second link between the FC networking device andthe second port when the first link and the second link are in the firsttrunk group.
 10. The IHS of claim 9, wherein the NPG engine is furtherconfigured to: establish a fourth fabric login between the first serverdevice and the FC networking device via the third port and the secondlink between the FC networking device and the second port when the firstlink is not available.
 11. The IHS of claim 9, wherein the NPG engine isfurther configured to: group, subsequent to the grouping of the firstlink and the second link, a third link between the FC networking deviceand a fourth port of the plurality of ports with the first link and thesecond link in response to receiving a third fabric login accept on thethird link that includes the first WWN associated with the FC networkingdevice such that the third link is added to the first trunk group,wherein the receiving the third fabric login accept completes a fourthfabric login that is between the FCF device and the FC networking devicevia the third link.
 12. The IHS of claim 11, wherein the NPG engine isfurther configured to: generate a first map of a virtual trunk instancethat includes a virtual trunk identifier mapped to the group of thefirst link and the second link, wherein the first map includes thevirtual trunk identifier that is associated with a first FC identifierassigned to the first port, the first WWN included with the first link,and a login type of the first link, and wherein the virtual trunkidentifier is associated with a second FC identifier that is assigned tosecond port, the first WWN of the second link, and a login type of thesecond link, and wherein the FC networking device is configured to:generate a second map of the virtual trunk instance that includes thevirtual trunk identifier mapped to the first link and the second link,wherein the second map includes the virtual trunk identifier that isassociated with the first FC identifier that is assigned to first port,the second WWN included with the first link, and the login type of thefirst link, and wherein the virtual trunk identifier is associated withthe second FC identifier that is assigned to the second port, the secondWWN of the second link, and the login type of the second link.
 13. TheIHS of claim 12, wherein the NPG engine is further configured to: removethe first link from the first map of the virtual trunk instance inresponse to identifying that the first link is no longer available, andwherein the FC networking device is configured to: remove the first linkfrom the second map of the virtual trunk instance in response toidentifying that the first link is no longer available.
 14. The IHS ofclaim 13, wherein the NPG engine is further configured to: provide, inresponse to identifying that the first link is no longer available,traffic from the first server device through the second link withoutlogging out the first server device.
 15. A method of load balancing on aFibre Channel Forwarder (FCF), comprising: grouping, by an Fibre ChannelForwarder (FCF) device, a first link between a Fibre Channel (FC)networking device and a first port of a plurality of ports on the FCFdevice with a second link between the FC networking device and a secondport of the plurality of ports in response to receiving both a firstfabric login accept on the first link that includes a first WorldwideName (WWN) associated with the FC networking device and a second fabriclogin accept on the second link that includes the first WWN associatedwith the FC networking device as a first trunk group, wherein thereceiving the first fabric login accept completes a first fabric loginbetween the first port on the FCF device and the FC networking devicevia the first link, and wherein the receiving the second fabric loginaccept completes a second fabric login between the second port on theFCF device and the FC networking device via the second link; receiving,by the FCF device, a third fabric login request from a first serverdevice on a third port of the plurality of ports on the FCF device;selecting, by the FCF device, the first link on the first port over thesecond link on the second port through which to log the first serverdevice into the FC networking device based on the third fabric loginrequest; establishing, by the FCF device, a third fabric login betweenthe first server device and the FC networking device via the third portand the first link between the FC networking device and the first port;and providing, by the FCF device, at least a portion of first traffic,received from the first server device via the third port and that isonly logged in to the FC networking device through the first linkbetween the FC networking device and first port, through the second linkbetween the FC networking device and second port when the first link andthe second link are in the first trunk group.
 16. The method of claim15, further comprising: establishing, by the FCF device, a fourth fabriclogin between the first server device and the FC networking device viathe third port and the second link between the FC networking device andthe second port when the first link is not available.
 17. The method ofclaim 15, further comprising: grouping, by the FC networking device, thefirst link between the FC networking device and the first port of theFCF device with the second link between the FC networking device and thesecond port of the FCF device as a second trunk group in response toreceiving both a first fabric login request on the first link thatincludes a second WWN associated with the FCF device and a second fabriclogin request on the second link that includes the second WWN associatedwith the FCF device; group the first link between the FC networkingdevice and the FCF device with the second link between the FC networkingdevice and FCF device in response to receiving both a first fabric loginrequest on the first link that includes a second WWN associated with theFCF device and a second fabric login request on the second link thatincludes the second WWN associated with the FCF device as a second trunkgroup, wherein the second trunk group causes the FC networking device toaccept at least the portion of the first traffic from the first serverdevice on the second link through which the first server device is notlogged in to the FC networking device.
 18. The method of claim 17,further comprising: generating, by the FCF device, a first map of avirtual trunk instance that includes a virtual trunk identifier mappedto the first link and the second link, wherein the first map includesthe virtual trunk identifier that is associated with a first FCidentifier assigned to a first node port of the FCF device providing thefirst link, the first WWN included with the first link, and a login typeof the first link, and wherein the virtual trunk identifier isassociated with a second FC identifier that is assigned to a second nodeport of the second link, the first WWN of the second link, and a logintype of the second link; and generating, by the FC networking device, asecond map of the virtual trunk instance that includes the virtual trunkidentifier mapped to the first link and the second link, wherein thesecond map includes the virtual trunk identifier that is associated withthe first FC identifier that is assigned to the first node port of theFCF device providing the first link, the second WWN included with thefirst link, and the login type of the first link, and wherein thevirtual trunk identifier is associated with the second FC identifierthat is assigned to the second node port of the second link, the secondWWN of the second link, and the login type of the second link.
 19. Themethod of claim 18, further comprising: removing, by the FCF device, thefirst link from the first map of the virtual trunk instance in responseto identifying that the first link is no longer available; and removing,by the FC networking device, the first link from the second map of thevirtual trunk instance in response to identifying that the first link isno longer available.
 20. The method of claim 19, further comprising:providing, by the FCF device and in response to identifying that thefirst link is no longer available, traffic from the first server devicethrough the second link without logging out the first server device.